content/docs/rest/03_rest_editor/_index.md (2)

351-386: Route id placement at the end differs from other examples.

In this route definition, the id: route-3988 appears at the end (line 385) rather than immediately after route: as shown in other documentation examples. While both are valid YAML, consistency across documentation helps readers.

📝 Optional: Move id for consistency

 - route:
+    id: route-3988
     from:
       uri: direct
       ...
         - log:
             id: log-2120
             message: "Books list: ${body}"
-    id: route-3988

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/docs/rest/03_rest_editor/_index.md` around lines 351 - 386, The route
definition places "id: route-3988" at the end of the block which differs from
other examples; move the id key to immediately follow the "route:" mapping
(i.e., place id: route-3988 directly under the route: key, before the from:
block) so the structure is consistent with other examples that show route id
first; ensure indentation and YAML validity are preserved and that the rest of
the mapping (from:, steps:, etc.) remains unchanged.

---

404-438: JSON comment syntax is invalid but acceptable for documentation.

The // ... more books comment on line 437 is not valid JSON syntax. However, this is acceptable in documentation to indicate truncated output. Consider using an alternative that's clearer:

📝 Optional: Use ellipsis notation

      }
    ]
-  }
-  // ... more books
+  },
+  ...
 ]

Or simply add a note after the code block instead.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/docs/rest/03_rest_editor/_index.md` around lines 404 - 438, Replace
the invalid JSON comment inside the JSON code block (the "// ... more books"
line) with a valid indicator: either remove the comment and add a trailing
ellipsis entry like an empty object or a comment outside the code block, or
replace it with a JSON-safe placeholder such as { "..." : "more books omitted" }
to keep the code block valid JSON; update the JSON example block shown in the
documentation (the JSON array example) and, if preferred, add a short note
immediately after the code block explaining that the output was truncated.

content/docs/rest/01_code_first/_index.md (1)

221-228: Minor: Extra blank line in bash code block.

There's an extra blank line at the beginning of this code block (line 222) before the # Frankenstein comment.

📝 Suggested fix

 ```bash
-
 # Frankenstein
 curl http://localhost:8080/books/84/fun-extract

 # The Adventures of Sherlock Holmes
 curl http://localhost:8080/books/1661/fun-extract

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

Verify each finding against the current code and only fix it if needed.

In @content/docs/rest/01_code_first/_index.md around lines 221 - 228, Remove the
extra blank line at the start of the bash code block so the first line after the
opening bash fence is the comment "# Frankenstein"; update the fenced block containing the two curl examples (the lines with "# Frankenstein" and "# The Adventures of Sherlock Holmes" and their curl commands) to begin immediately after bash with no leading empty line.

</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>🤖 Prompt for all review comments with AI agents</summary>

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @content/docs/rest/01_code_first/_index.md:

• Around line 150-151: The log message currently contains nested quotes ('"Book
  summary: ${body}"') under the log -> message key; remove the extra surrounding
  single quotes so the message reads "Book summary: ${body}" (or use a
  single-quoted literal 'Book summary: ${body}' if preferred) and update the YAML
  value for the log.message entry accordingly; if the literal inner quotes were
  intentional instead of removed, add a brief note explaining why the output must
  include literal quotation marks near the log example.

In @content/docs/rest/02_designer_first/_index.md:

• Around line 181-184: The log step in the intermediate example uses
  nested/extra single quotes around the message (the log: message: '"Book summary:
  ${body}"') which is inconsistent with the final example; update the log message
  to remove the outer single quotes so the log's message value matches the final
  example ("Book summary: ${body}"), and keep the adjacent setBody constant
  (Operation getBookFunExtract not yet implemented) unchanged; locate the log step
  by the keys "log", "message" and "setBody" to correct the string formatting.

---

Nitpick comments:
In @content/docs/rest/01_code_first/_index.md:

• Around line 221-228: Remove the extra blank line at the start of the bash code
  block so the first line after the opening bash fence is the comment "# Frankenstein"; update the fenced block containing the two curl examples (the lines with "# Frankenstein" and "# The Adventures of Sherlock Holmes" and their curl commands) to begin immediately after bash with no leading empty line.

In @content/docs/rest/03_rest_editor/_index.md:

• Around line 351-386: The route definition places "id: route-3988" at the end
  of the block which differs from other examples; move the id key to immediately
  follow the "route:" mapping (i.e., place id: route-3988 directly under the
  route: key, before the from: block) so the structure is consistent with other
  examples that show route id first; ensure indentation and YAML validity are
  preserved and that the rest of the mapping (from:, steps:, etc.) remains
  unchanged.
• Around line 404-438: Replace the invalid JSON comment inside the JSON code
  block (the "// ... more books" line) with a valid indicator: either remove the
  comment and add a trailing ellipsis entry like an empty object or a comment
  outside the code block, or replace it with a JSON-safe placeholder such as {
  "..." : "more books omitted" } to keep the code block valid JSON; update the
  JSON example block shown in the documentation (the JSON array example) and, if
  preferred, add a short note immediately after the code block explaining that the
  output was truncated.

</details>

<details>
<summary>🪄 Autofix (Beta)</summary>

Fix all unresolved CodeRabbit comments on this PR:

- [ ] <!-- {"checkboxId": "4b0d0e0a-96d7-4f10-b296-3a18ea78f0b9"} --> Push a commit to this branch (recommended)
- [ ] <!-- {"checkboxId": "ff5b1114-7d8c-49e6-8ac1-43f82af23a33"} --> Create a new PR with the fixes

</details>

---

<details>
<summary>ℹ️ Review info</summary>

<details>
<summary>⚙️ Run configuration</summary>

**Configuration used**: Organization UI

**Review profile**: CHILL

**Plan**: Pro

**Run ID**: `d636ee13-a03f-4547-8eea-6a3bfceccba5`

</details>

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between e9b322bb8fd8d6ebe16a93db6a3137ba2ed34d3d and 5d5e02cb85775247e193664063c59c57defca2c8.

</details>

<details>
<summary>⛔ Files ignored due to path filters (16)</summary>

* `content/docs/rest/01_code_first/complete-route.png` is excluded by `!**/*.png`
* `content/docs/rest/01_code_first/rest-actions.png` is excluded by `!**/*.png`
* `content/docs/rest/01_code_first/settings1.png` is excluded by `!**/*.png`
* `content/docs/rest/01_code_first/settings2.png` is excluded by `!**/*.png`
* `content/docs/rest/02_designer_first/after-drag-and-drop.png` is excluded by `!**/*.png`
* `content/docs/rest/02_designer_first/complete-route.png` is excluded by `!**/*.png`
* `content/docs/rest/02_designer_first/imported-route.png` is excluded by `!**/*.png`
* `content/docs/rest/02_designer_first/rest-import-button.png` is excluded by `!**/*.png`
* `content/docs/rest/02_designer_first/rest-import-generation.png` is excluded by `!**/*.png`
* `content/docs/rest/02_designer_first/rest-import-wizard-1.png` is excluded by `!**/*.png`
* `content/docs/rest/02_designer_first/rest-import-wizard-2.png` is excluded by `!**/*.png`
* `content/docs/rest/03_rest_editor/add-operation-modal.png` is excluded by `!**/*.png`
* `content/docs/rest/03_rest_editor/duplicate-component.png` is excluded by `!**/*.png`
* `content/docs/rest/03_rest_editor/final-route.png` is excluded by `!**/*.png`
* `content/docs/rest/03_rest_editor/new-route-created.png` is excluded by `!**/*.png`
* `content/docs/rest/03_rest_editor/rest-form.png` is excluded by `!**/*.png`

</details>

<details>
<summary>📒 Files selected for processing (5)</summary>

* `content/docs/rest/01_code_first/_index.md`
* `content/docs/rest/02_designer_first/_index.md`
* `content/docs/rest/03_rest_editor/_index.md`
* `content/docs/rest/_index.md`
* `content/docs/rest/book-summary-api.openapi.yaml`

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

content/docs/rest/02_code_first/_index.md (1)

181-183: ⚠️ Potential issue | 🟡 Minor

Use consistent log message formatting in both YAML snippets.

Both examples still use nested quotes ('"Book summary: ${body}"'), which is inconsistent with the surrounding guidance and can confuse readers.

📝 Suggested fix

         - log:
-            message: '"Book summary: ${body}"'
+            message: "Book summary: ${body}"
...
         - log:
-            message: '"Book summary: ${body}"'
+            message: "Book summary: ${body}"

Also applies to: 288-289

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/docs/rest/02_code_first/_index.md` around lines 181 - 183, Replace
the nested-quoted log message in the YAML examples so they use the same simple
quoting as the rest of the doc: update the log message value that currently
appears as '"Book summary: ${body}"' to "Book summary: ${body}" (remove the
extra single quotes) and make the corresponding change in the other snippet that
also contains the nested-quoted value; ensure the 'log: message' entries and
nearby 'setBody' examples use the consistent quoting style.

content/docs/rest/01_api_first/_index.md (1)

153-154: ⚠️ Potential issue | 🟡 Minor

Normalize the log message quoting in the YAML example.

At Line 154, message: '"Book summary: ${body}"' is inconsistent with the instruction text (Line 122) and adds avoidable confusion for copy/paste users.

📝 Suggested fix

         - log:
-            message: '"Book summary: ${body}"'
+            message: "Book summary: ${body}"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/docs/rest/01_api_first/_index.md` around lines 153 - 154, The YAML
example uses inconsistent nested quotes for the log message (message: '"Book
summary: ${body}"'); update the YAML `message` value to use a single set of
quotes consistent with the instruction text (e.g., message: "Book summary:
${body}" or message: 'Book summary: ${body}') so the example is clear and
copy/paste-ready—look for the `message` YAML key in the example block and
replace the double-wrapped string with a single-quoted or double-quoted string.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

content/docs/rest/01_api_first/_index.md (1)

154-154: Simplify log message formatting by removing nested quotes.

Line 154 uses nested quotes '"Book summary: ${body}"', which causes literal quotation marks to appear in the log output. Standard YAML formatting "Book summary: ${body}" is simpler and more consistent with typical Camel examples.

📝 Suggested fix

         - log:
-            message: '"Book summary: ${body}"'
+            message: "Book summary: ${body}"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/docs/rest/01_api_first/_index.md` at line 154, Change the YAML value
for the message key to remove the extra outer single quotes so it becomes a
normal double-quoted string; specifically update the message entry currently
written as '"Book summary: ${body}"' to "Book summary: ${body}" so the log does
not include literal quotation marks (look for the message: entry in this
document).

content/docs/rest/03_rest_editor/_index.md (1)

195-195: Simplify log message formatting by removing nested quotes.

Lines 195 and 352 use nested quotes '"Book summary: ${body}"', which causes literal quotation marks to appear in the log output. Standard YAML formatting "Book summary: ${body}" is simpler and aligns with typical Camel examples.

📝 Suggested fix

         - log:
-            message: '"Book summary: ${body}"'
+            message: "Book summary: ${body}"

Apply this change at both line 195 and line 352.

Also applies to: 352-352

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/docs/rest/03_rest_editor/_index.md` at line 195, Replace the
nested-quoted log message values that currently read message: '"Book summary:
${body}"' with a normal double-quoted YAML string message: "Book summary:
${body}" at both occurrences (the two message keys shown in the diff), so the
logged output doesn't include literal extra quotation marks; locate the two
"message" entries in the document (one around the first occurrence and the
second around the later occurrence) and change their values accordingly.

content/docs/rest/book-summary-api.openapi.yaml (1)

1-48: Note: Security omitted for local development example.

The OpenAPI specification does not define security schemes. While this is acceptable for a localhost development tutorial, in production APIs you should include security definitions (API keys, OAuth2, etc.) to protect your endpoints.

Static analysis tools correctly flag this (CKV_OPENAPI_4, CKV_OPENAPI_5), but for this documentation example focused on Kaoto's REST features, the omission is reasonable.

Based on learnings: Static analysis hints should be evaluated in context—for tutorial code running locally, missing security is a teaching trade-off rather than a blocker.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/docs/rest/book-summary-api.openapi.yaml` around lines 1 - 48, The
OpenAPI spec currently lacks security definitions; add a security scheme under
components.securitySchemes (e.g., ApiKeyAuth or OAuth2) and reference it via a
global components.security or per-operation security array for the
/books/{id}/fun-extract operation (operationId getBookFunExtract) so static
analyzers stop flagging CKV_OPENAPI_4/5; implement a clear scheme name (e.g.,
ApiKeyAuth) and ensure the security requirement uses that exact name to tie the
scheme to the endpoint.

content/docs/rest/02_code_first/_index.md (1)

182-182: Simplify log message formatting by removing nested quotes.

Lines 182 and 289 use nested quotes '"Book summary: ${body}"', which causes literal quotation marks to appear in the log output. Standard YAML formatting "Book summary: ${body}" is simpler and more typical in Camel examples.

📝 Suggested fix

         - log:
-            message: '"Book summary: ${body}"'
+            message: "Book summary: ${body}"

Apply this change at both line 182 and line 289.

Also applies to: 289-289

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/docs/rest/02_code_first/_index.md` at line 182, The log message
entries use nested single+double quotes causing literal quotes to appear (e.g.
the message key currently set as '"Book summary: ${body}"'); update both
occurrences of the message key (the two message entries around lines 182 and
289) to use a single double-quoted YAML string like "Book summary: ${body}" so
the template variable interpolates without extra quotation characters.

content/docs/rest/01_api_first/_index.md (1)

110-111: ⚠️ Potential issue | 🟡 Minor

Log message still has extra nested quotes.

Line 111 still wraps the message with extra single quotes, which likely produces unintended literal quotes in output and conflicts with the earlier instruction format.

🛠️ Proposed fix

         - log:
-            message: '"Book summary: ${body}"'
+            message: "Book summary: ${body}"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/docs/rest/01_api_first/_index.md` around lines 110 - 111, The log
entry under the log block uses message: '"Book summary: ${body}"' which contains
extra nested single quotes; update the log.message value to remove the outer
quotes so the template is not wrapped in literal quotes (i.e., adjust the log
block's message key to use a plain quoted template like "Book summary: ${body}"
or an unquoted template as appropriate), ensuring the log.message field no
longer contains the extra single quotes.

content/docs/rest/_index.md (1)

12-16: Clarify approach count to avoid reader confusion.

Line 12 says “two distinct approaches,” but this page also links a dedicated REST Editor guide (Line 15 and “Choose Your Approach” context). Consider wording this as “three workflows” or explicitly stating REST Editor is part of the code-first track.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/docs/rest/_index.md` around lines 12 - 16, Update the intro copy that
currently says "two distinct approaches" to remove confusion: either change it
to "three workflows" (API-First, Code-First, REST Editor) or explicitly state
that the "REST Editor" is a sub-workflow of the Code-First approach; edit the
text around the list items (the sentence introducing the list and the entries
for "Code-First Approach" and the REST Editor link) so the count and
relationship are consistent (e.g., "three workflows" or "two approaches — with
the REST Editor as part of Code-First").

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

content/docs/rest/01_api_first/_index.md (1)

110-111: ⚠️ Potential issue | 🟡 Minor

Log message includes unnecessary nested quotes.

message: '"Book summary: ${body}"' is inconsistent with the earlier instruction (Book summary: ${body}) and likely unintentional.

Suggested fix

-        - log:
-            message: '"Book summary: ${body}"'
+        - log:
+            message: "Book summary: ${body}"

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@content/docs/rest/01_api_first/_index.md` around lines 110 - 111, The log
entry under the log key uses unnecessary nested quotes: replace the value
currently set as '"Book summary: ${body}"' for the message field so it becomes a
plain string "Book summary: ${body}" (i.e., remove the extra surrounding quotes)
in the log -> message entry to match the earlier instruction.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes